home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Collection of Tools & Utilities
/
Collection of Tools and Utilities.iso
/
comm
/
lib232.zip
/
NEW-FEAT.DOC
< prev
next >
Wrap
Text File
|
1990-10-14
|
53KB
|
980 lines
NEW-FEAT.DOC Copyright (C) 1990 Liberation Enterprises.
Features introduced in The Liberator v2.3.
This document is not just a quick listing, but items are explained in
some detail to allow veteran Liberator users to attempt to avoid
printing the larger manual. Things are covered more fully in the larger
manual, but this document lists all the important new features, and will
give you a good idea how to make use of them. After a few days of
exploring, (or if you run into a problem) you should then selectively
browse the larger manual (esp. the section 'Using The Master', and the
'Custom Command', 'File Transfers' sections).
Registration Gimmicks?
There is now a Registered Version of The Liberator, for a number of
reasons. The distribution (unregistered) version of the program now
has evaluation copy reminder screens -- not to annoy you, but simply
because I feel that without such reminders, people actually forget to
register. In the registered version, the reminders are removed. As
well, each registered copy comes with a serial number, which makes it
easier for myself, and vendors to control sales of the program. The
serial numbers were actually the initial reason to create a registered
version, but with a registered version created, the reminder screens
became an obvious addition to the unregistered version.
Color configuration is also possible with the registered version of The
Liberator v2.3, so send away for your registered copy today!
10-14-90 Release 2.32. Maintenance release. Due to code (and time)
restraints, this release of The Liberator was cut short and
not all features planned were added. If you made a suggestion
for improvement, and it did not show up in this release,
please look for it in v3.0, which is going back into
development immediately. Version 3.0 was started months ago,
but in mid-development many changes were made to PCBoard
(ProLogon, PCBoard v14.5, multiple Qmail doors, etc) and it
became necessary to pull v2.2 out of the archives to support
the new items, as v3 could not have been released in time.
Version 2.32 was meant only to fill the gap, and meet your
needs until the rest of version 3 can be completed. Though it
is realized that improvements could be made in certain areas
of v2.3, it is felt that time would be better spent moving
back to v3 immediately, instead of attempting to modify the
obsolete v2 code any further.
Having said this, if you are not registered *please* do not
wait for v3 to be released before you send in your support for
the program (assuming your evaluation of v2.3 is successful
and you continue using the program). Version 3 may be quite a
while coming, and your support is needed today to allow it to
be developed. All v1.x and v2.x registrants will be eligible
for low-cost upgrading to v3 at a sizeable discount to full
registration, so you really can't lose by sending your
registration today.
The L i b e r a t o r v2.31 NEW-FEAT.DOC - Page 2
Version 2.32 New Features and Fixes:
+ Qmail v4, NetMail, MegaMail, and PCRelay support added. See MAIL.DOC,
also new in v2.32, for information on setting up for the various Qmail
doors. Qmail PTR (pointer reset) files are now automatically
maintained along with the REP file.
+ The RunMaster program has changed quite a bit from v2.31. While
running the Master list, RunMaster now keeps track of how many dialing
attempts have been made per board, and removes each job from the queue
when the total dial attempts reaches the 'Redial Attempts' number, set
in each BBS Configuration (screen 1, item 4). If 'Redial attempts' is
set to 0, the job remains in the Master queue indefinitely (until it
completes or aborts due to an error). If it is set to any other
number, the job is dialed in increments of 'Master Redial Attempts',
until the total is reached. Thus, 'Redial attempts' works as it
normally does, but RunMaster cycles to the next job every 3 attempts,
and keeps a running total for each job (3 being whatever you have set
in 'Master redial attempts' using the Tools item). When only one job
remains in the queue (when all others have completed or aborted), any
remaining redial attempts for that job are carried out all at once,
instead of dialing in increments of the 'Master redial' value.
Once you see it in operation it will become pretty clear what this all
means. It was added only for those who want to put a limit on the
number of attempts certain jobs make. If you have your 'Redial
attempts' item in each Configuration set to 0 (until connect) then
none of the above will apply, and each job will remain in the queue
until it completes, or aborts due to an error.
+ Two abort code values allow a Command File to remain in the Master
queue. Namely values 28 (connection lost) and 29 (bad logon attempt).
There was extra protection built into RunMaster v2.31 for these abort
values, which was supposed to remove the Command File from the queue
after 3 contiguous returns of either value on any given Command File.
However, this protection was not working properly, and RunMaster
continued to keep these jobs in the queue even after 3 bad returns.
If your online time had expired at a BBS for the day, (which causes a
bad logon attempt, or Abort Code 29), RunMaster did not remove the job
from the queue after 3 attempts, which meant the board could be called
back many times.
This has been fixed, and any bad logon attempt (logging onto a 'down'
node, etc.) or << Connection Lost >> in the middle of a session,
causes RunMaster to start a counter for that job, and it will properly
remove the job after 3 bad returns. Note that 3 attempts are allowed,
in case the connection is inadvertantly lost due to line-noise, etc.,
or in case of simply attempting to log onto one 'down' node of a
multi-node BBS system. For these cases, the 2nd or 3rd retry may save
your session. If not, the job is removed from the Master queue and
will not be tried again until the next Master run.
+ Master Dial delays were sometimes not working properly when used in
The L i b e r a t o r v2.31 NEW-FEAT.DOC - Page 3
tandem with REPEAT commands. If all jobs in the queue completed
within one hour, the delay was not observed (due to the fact that
Master Dial delays are good for up to an hour, to allow for over-
runs... see the manual for more details). This has now been fixed,
and the one hour leeway does not apply immediately after a REPEAT.
The one hour leeway still applies for all other cases.
+ Added support for PCBoard v14.5 batch protocol entry. If you have The
Liberator set up for PCBoard 14.5/batch mode (file transfers using the
UB/DB commands), and your 'default' PCBoard protocol on the BBS was
set to 'None', PCBoard asks for a protocol to use, just after The
Liberator finishes entering filenames. Previously, The Liberator
ignored this prompt, and simply sent a CR (PCBoard assumes 'N'one as
the protocol if this is done). However, you may now enter specific
protocol letters in your BBS Configurations (see CFG